Fix user attribute fallback #11
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For some of the omniauth user attributes that omniauth-ldap fetches from the LDAP server we have a list of fallback options in case an attribute is missing, for example:
This means that if the LDAP object for the user does not have a
mail
attribute, omniauth-ldap will try theemail
attribute, and then theuserPrincipalName
attribute.This attribute fallback was broken. In this PR we cherry-pick the upstream commits that fix this functionality, and we modified the tests to catch future regressions.